Single-Use Multi-Layered Ticket and Redeeming Technique

ABSTRACT

A ticket for managing cryptocurrency. The ticket incorporates a redeeming code in combination with a loading code for activating the redeeming code. At the same time, however, the loading code also prohibits access to the underlying redeeming code, thereby preventing use. Therefore, in order to access the redeeming code and redeem the ticket of cryptocurrency, the loading code is inherently destroyed by removal. Thus, the ticket is no longer practically able to be re-loaded and is thus, single-use, thereby aiding in user understanding and management of cryptocurrency.

BACKGROUND

As a matter of user convenience, electronically transferring value tofurther transactions has been emerging for decades, largely overtakingharder currency funded exchanges such as the transfer of cash or a checkfrom a purchaser to a retail seller. Indeed, even many check fundedtransactions now take place in a partially electronic, real-time mannerwith the check accepted by the retailor being wirelessly posted to thepurchaser's account at the very time of the transaction.

Of course, as opposed to merely being partially electronic, as in thereal-time posting of a check, it is even more common for a purchaser toutilize debit or credit cards to fund the transaction. Thesetransactions are funded without the exchange of any instrument betweenthe purchaser and the seller. Instead, the transaction remains entirelyelectronic with the purchaser effectively transferring value to theseller without the transfer of any physical instruments. Instead, amagnetic strip of the card is automatically read at the point ofpurchase in order to fund the transaction. This affords a level ofreal-time added convenience for the transaction. For example, thepurchaser need not keep track of or fill out physical instruments inorder to complete the transaction. Once more, the completion of thetransaction automatically updates the seller and purchaser accounts.

Similar to credit and debit “card” transactions, internet and mobiledevice transactions often take place without the use of a physical cardat all. That is, as opposed to physically using a magnetic strip of ahandheld card, card-type account information may be supplied in otherways. In the case of an internet purchase, the account information maybe manually supplied at a user interface and managed by a server inorder to complete a debit or credit transaction. As a matter of evenmore convenience, an “app” on a smartphone may be utilized toautomatically supply such information at the point of sale via nearfield communication. In this circumstance, the card is replaced by amobile device that the user is already likely to be carrying on person.Thus, not only is the use of a more cumbersome card avoided, but so isthe need to manually supply the account information as in the notedinternet transaction.

Unfortunately, unlike the transfer of a purely liquid asset such asgold, the above modes of transferring value from one user to anotherthat utilize an alternative instrument or electronic transfer requiremanagement or backing by a centralized institution. This is particularlytrue for the purely electronic transactions. That is, unlike cash, whicheven though backed by a government body may become near liquid inexchangeability, electronic transfers generally take place betweenfinancial institutions. Thus, for a purchaser, a seller or anyoneseeking to transfer electronic value, a host of fees for managing theaccount and each transfer are generally involved. This often has adisproportionate impact on the smaller dollar account holders. Indeed,rather than pay a host of different account and transaction fees,someone with under $1,000 in total funds is generally more likely tokeep these funds in tangible cash and avoid such fees as compared tosomeone with over $10,000 in total funds.

However, recent developments in crypto-currencies such as Bitcoin allowanyone, including smaller funded individuals, to deal in electroniccurrency without facing the transactional fees and other costs oftenassociated with electronic currency exchanges. This is due to the factthat crypto-currency is decentralized, without any need for anintermediate party to regulate the transaction. No governmental orbanking body is required in order to issue, guarantee or regulate theelectronic instrument for the transaction. Rather, once the Bitcoin, isacquired by the user, it may be directly electronically exchanged “peerto peer” with another user. Thus, Bitcoin is able to serve as anelectronic cash system that does not disproportionately impact the userwho has a generally smaller available amount of funds.

Unfortunately, there is a real difficulty for the non-technical user tobe able to be part of a crypto-currency system. That is, even thoughmore and more smaller funded users have access to computers andsmartphones than ever before, it remains quite common that they do nothave the skill required to operate in the crypto-currencies realm.Indeed, this often remains a challenge for more well-funded users aswell. Presently, operating with crypto-currencies requires theunderstanding of abstract concepts such as asymmetric cryptography, aswell as the protocols used to acquire, store and transmit value securelyusing this digital intangible system. The end result is that users whomight greatly benefit continue to opt for cash modes or electronic feemodes.

Efforts have been undertaken to simplify cryptocurrencies by introducinga tangible medium. For example, it is possible to downloadcryptocurrency from traditional storage locations such as a computer toa card or coin-shaped device with electronic storage capacity. Thisprovides the user with a familiar cash-like handheld instrument formanaging the cryptocurrency.

Unfortunately, unlike cash, the electronic instrument does not leave theuser when it is spent. This introduces a unique set of challenges forcryptocurrency. Specifically, it may not be immediately apparent if thetangible cryptocurrency instrument is loaded with any value or to whatextent. Indeed, given its electronic nature, the loaded value of theinstrument is likely to fluctuate as a user adds, spends and thenre-loads the instrument. Thus, while on one hand things have becomefamiliar and simplified, on the other hand, the instrument has justintroduced a brand new complexity. Ultimately, lacking a more effectivesimplification tool, the smaller funded, less technical users that mightbenefit the most from cryptocurrency use remain unlikely to participatein the cryptocurrency realm.

SUMMARY

A multi-layered single-use ticket is provided. The ticket may include ahandheld substrate with a redeeming material layer printed at a surfacelocation thereon. The printed redeeming material layer may include atleast one redeeming code for accessing and using by the user. Further,the ticket includes a printed loading material layer masking theredeeming code to simultaneously prohibit the accessing and enable theusing. At the same time, the loading material layer is removable tosimultaneously enable the using and substantially disable subsequentusing of the redeeming code by way of loading code activation.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a front view of an embodiment of a multi-layered single-usecryptocurrency ticket.

FIG. 2A is a front perspective view of the ticket of FIG. 1 revealing anunderlying redeeming material layer thereof.

FIG. 2B is a side cross-sectional view of the ticket of FIG. 1simultaneously revealing a masking loading material layer over theredeeming material layer.

FIG. 3A is a front view of the ticket of FIGS. 1 and 2A revealing theunderlying redeeming material layer with partial scratch-off remains ofthe loading material layer.

FIG. 3B is a back view of the ticket of FIG. 3A revealing indicatormarks corresponding to a scratch-off of the loading material layer atthe opposite side of the ticket.

FIG. 4 is an embodiment of a mobile user interface screen displaying anapplication for use with a single-use cryptocurrency ticket.

FIG. 5 is a depiction of another page of the application of FIG. 4 forredeeming cryptocurrency via interfacing with the redeeming materiallayer thereof.

FIG. 6A is a flow-chart summarizing an embodiment of manufacturing theticket of FIG. 1.

FIG. 6B is a flow-chart summarizing an embodiment of using the ticket ofFIG. 1.

DETAILED DESCRIPTION

In the following description, numerous details are set forth to providean understanding of the present disclosure. However, it will beunderstood by those skilled in the art that the embodiments describedmay be practiced without these particular details. Further, numerousvariations or modifications may be employed which remain contemplated bythe embodiments as specifically described.

Embodiments are described with reference to certain types ofcryptocurrency tickets for recording storage and redeeming ofcryptocurrencies. More specifically, embodiments of tickets,applications and techniques are detailed for management and transfer ofcryptocurrency. However, a host of other non-cryptocurrency informationcoding, storage and transfers may benefit from the tickets, applicationsand techniques detailed herein. For example, rights related to access,title transfers, wills or probate, various assets and other non-currencyinstruments may incorporate embodiment features and techniques taughtherein. Regardless, so long as a loading code is provided over aredeeming code so as to simultaneously enable the use of the loadingcode while prohibiting user access thereto and at the same time beingremovable to enable a one-time only use of the redeeming code,appreciable benefit may be realized.

For embodiments detailed below, this is illustrated with a removable“scratch-off” form of loading code or loading material layer. However, aremovable sticker, temporary paper covering or other form of materialmay be utilized. In such embodiments, it may be beneficial to have suchcoverings be self-destructive upon removal, for example, in the form ofsingle-use scored stickers.

Referring now to FIG. 1, a front view of an embodiment of amulti-layered single-use ticket 100 is shown. In the embodiment shown,the ticket 100 is a cryptocurrency ticket directed at aiding in themanagement of cryptocurrency by one or more users. However, as alludedto above and detailed further below, embodiments of such a ticket 100may be useful as an aid in managing or tracking a host of differenttypes of information, whether monetary in nature or otherwise.Additionally, while referred to as a “ticket” 100, this may include acryptocurrency instrument that generally ranges from a smaller note sizeof between about 2-3½ inches by 4-6¼ inches. This may correspond to aconventional US or Canadian bill or perhaps a “golden ratio” of about1.618, adding to tangible familiarity for a user. Of course, dependingon the application, larger standard letter, legal or A4 document sizesmay be utilized for the ticket 100. Similarly, depending on a host ofdifferent factors, the ticket 100 may primarily constitute a lightweightpaper document, heavier cardstock-type document or be of primarily hardpolymer construction similar to a conventional debit or credit card.

With added reference to FIGS. 2A and 2B, in terms of what the ticket 100primarily constitutes as noted above, it is an article manufactured ofdifferent layers. Specifically, the ticket 100 includes a substrate 275which may be the largest layer, if not the majority of the overallticket's thickness. Other compositional layers for at least a portion ofthe ticket 100 may include a printed redeeming material layer 220 on thesubstrate 275 and a printed loading material layer 101 masking over theunderlying redeeming material layer 220. Marking layers 280, 290 mayalso be utilized as detailed below as well as others. Overall, thedifferent layers, particularly the material 101, 220 and marking 280,290 layers may be manipulated by a user in conjunction with each otherin a machine like fashion. Specifically, the ticket 100 may beconsidered an article or even a single-use machine that supports uniquemethods of information tracking or accounting. Along these lines,exemplary embodiments herein are directed at using the ticket 100 as anaid for cryptocurrency information tracking and accounting, though othertypes of information may be managed with such a ticket 100 as indicatedabove.

Continuing with reference to FIG. 1, the ticket 100 is shown in anembodiment for cryptocurrency management as noted. Thus, a variety ofdifferent instructions 140 and notations such as the purchase price 175or cryptocurrency value of the ticket 100 may be shown at variouslocations. Other design features may be incorporated into the ticket 100to promote association with funds management. For example, in the US aportrait of a “founding father”, Harriet Tubman, or another historicalfigure may be included whereas in other locations, the ticket 100 maydisplay another person of historical interest. Perhaps even ad space 350may be provided (e.g. at the backside 325 of the ticket 100 (see FIG.3B)).

As indicated above and shown at FIG. 1, a loading material layer 101 isprovided that incorporates an image of a loading code 150. In theembodiment shown, this code is a QR (“quick response”) code. However, abar code or other electronically readable identifier may be utilized.Regardless, in an embodiment where the ticket 100 is to serve as an aidin tracking, transferring or otherwise managing cryptocurrency such asBitcoin, this code 150 may serve as an identifier which provides a linkto a public key corresponding to a public Bitcoin ledger. While thiscode 150 is public, it is generated simultaneous with one or moreprivate redeeming codes 250, 255, 257 (see FIG. 2A). These codes 250,255, 257 are not only non-public but they are masked by the material ofthe loading material layer 101 as detailed further below. Forcryptocurrency uses, these codes 250, 255, 257 are privately activatedfor use by loading of the loading code 150 as described herein for aspecific non-public amount.

When utilized for the management of cryptocurrency, the ticket 100 isinitially of no given value. Rather, it is no more than an instrumenthaving one visible code 150 covering over a related underlying code 250(or 255 or 257) (see FIG. 2A). However, none of these codes 150, 250,255, 257 are initially of any value or usefulness in and of themselves.In fact, even when utilized for “loading” or “redeeming”, the ticket 100itself does not literally loaded with, or redeemed of, Bitcoin, forexample. Instead, the ticket 100 may be considered a single-use,machine-like management tool for authorizing the acquisition and/ortransfer of Bitcoin as recorded at an electronic ledger. However, due tothe ability of the ticket 100 to serve as this type of authorizationaid, it may be considered to be of value once “loaded” as noted.

With brief added reference to FIG. 2A, as indicated above, the loadingcode 150 serves as a removable covering over a redeeming code 250 asalso discussed further below. However, in other embodiments, the loadingcode 150 may not be removable but instead printed or otherwise providedat the same time as the redeeming code 250. For example, this mayenhance manufacturability due to the informational relationship betweenthe codes 150, 250 as also described further below. Nevertheless, insuch embodiments, another covering layer may still be provided as a maskover the underlying redeeming code 250. In this way, removal of thisother covering may also serve as an indicator to potential users ofprior access to the redeeming code information. That is, in eithercircumstance, the user may be made aware of the likely spent nature ofthe ticket 100. Thus, with the covering removal as an indicator, theticket 100 is effectively single-use as a practical matter from theperspective of potential users.

Continuing with reference to FIG. 1, loading, activating or renderingthe ticket 100 “live” may be achieved in a variety of manners. Forexample, in one embodiment, in addition to other information encodedwithin the loading code 150, personalized information corresponding toan authorized electronic reader of an authorized seller or distributormay be found. Thus, a retailer having authority to “load” the ticketwith a particular amount of cryptocurrency may utilize a personalapplication and/or code reader to activate the ticket 100. So, forexample, a particular amount of Bitcoin may be loaded onto the ticket100 by the authorized seller/retailer as reflected by recording at thepublic ledger. Indeed, the application utilized by the retailer may bothacquire Bitcoin for the retailer and load the Bitcoin to the ticket 100in a near simultaneous fashion such that the retailer need not maintaina separate substantial amount of Bitcoin funds for sake of ticket sales.

Depending on particular design and business objectives, the ticket 100may include a host of additional features. For example, given that theticket 100 is of no particular value until loaded there may be no greatconcern over tracking and monitoring ticket locations in advance ofbeing loaded by an authorized retailer. Nevertheless, for sake ofkeeping tabs on inventory, marketing or to allow follow-on action incase of lost tickets 100, they may be provided with readily traceableserial numbers or have unique lot-type information embedded within eachloading code 150. Additionally, due to the capabilities of the loadingcode 150, anti-counterfeit measures such as use of a hologram,micro-writing or other efforts may be used to help prevent copying ofthe code 150.

Referring now to FIG. 2A, a front perspective view of the ticket 100 ofFIG. 1 is shown revealing the above referenced redeeming material layer220. That is, the coded region 125 of the ticket 100 includes aredeeming material layer 220 with at least one redeeming code 250, 255,257 located below the loading material layer 101 of FIG. 1. Thus, in theview of FIG. 2A, the redeeming layer 220 and codes 250, 255, 257 arevisible and accessible due to sufficient removal of the loading materiallayer 101 and code 150 thereabove. That is, the ticket 100 mayconstitute a printable substrate 275 with varying layers thereover (orbelow). Depending on whether or not the loading material layer 101 withcode 150 is present or not at the coded region 125, the appearance ofthe ticket surface 225 may change.

As indicated above, with the loading code 150 present, the ticket 100may be “loaded” with cryptocurrency. However, upon removal of theloading code 150 of FIG. 1, the ticket 100 may no longer be loaded viathe most practical means of the dedicated loading code 150. Indeed, inone embodiment, the loading 150 and redeeming 250 codes, perhaps alongwith an electronic application (e.g. see 401 of FIG. 4) may be tailoredtogether to prohibit loading except via the in-tact, dedicated loadingcode 150. Regardless, even in absence of such extensive measures, from auser standpoint, for all intents and purposes, removing of the loadingmaterial layer 101 and code 150 substantially avoids further loading ofthe ticket 100 with cryptocurrency.

At the same time, however, this removing is nevertheless required inorder to use or “redeem” the cryptocurrency from the ticket 100 via oneof the underlying redeeming codes 250, 255, 257. Therefore, the removingof the loading material layer 101 and code 150 means that not only issubsequent reloading substantially stopped, but so to is subsequentredeeming. The ticket 100 is thus, a single-use, machine-like implement,in this embodiment for the management of cryptocurrency. Stated anotherway, completed use of the ticket 100 inherently leads to its ownself-destruction and prevention from further use as a practical matter.As a result, the user is provided with a uniquely understandablemanagement tool that may be of particular benefit for complextransactions such as those in the realm of cryptocurrency.

Continuing with reference to FIG. 2A, the redeeming codes 250, 255, 257may be interchangeable and redundant from the user's perspective butthey are also tied to one another regardless of which one is utilized.That is, when the user redeems one of the codes 250, 255, 257, forexample through a mobile or other application as detailed further below,all of the codes 250, 255, 257 will be simultaneously redeemed. By wayof specific example, when the depicted QR visual code 250 is used forredemption, the visual 250, alphanumeric 255 and auditory 257 codes willall be simultaneously disabled from further use.

As to the distinctions between the redemption codes 250, 255, 257, avariety of options are made available to the user. That is, unlike theloading code 150 of FIG. 1, which is likely to be managed and utilizedfor loading by a retailer or merchant, the redemption codes 250, 255,257 may be utilized by a wider variety of user types. Thus, a visualcode 250 may be provided for a person seeking redemption through amobile phone application and wallet that interfaces with a QR code (seeFIG. 5). Once more, as opposed to redemption through the user's personalmobile application, the visual code 250 may be sent to another user forredemption. Indeed, along these lines, auditory 257 or alphanumeric 255codes may also be phoned, e-mailed or texted to distant locations forredemption by an entirely different end user.

Providing the code 250, 255, 257 to another location for use may be ofparticular benefit where the end user (or the ticket purchaser) fails tohave access to such technology but is nevertheless able to interfacewith a local merchant or retailer that does. So, for example, the partyacquiring the ticket 100 may send the redemption code 250, 255, 257 tothe end user or distant merchant in privy with the end user to allow theend user to redeem the code 250, 255, 257 for local currency from thedistant merchant. In these types of circumstances, the ticket 100 hasserved as an intermediate cryptocurrency platform for users otherwiseunable to participate in cryptocurrency transfers. Regardless, once thisredemption takes place through any of the codes 250, 255, 257, theticket 100 is no longer of any practical value.

Referring now to FIG. 2B, a side cross-sectional view of the ticket 100of FIG. 1 is shown that simultaneously reveals the masking loadingmaterial layer 101 over the redeeming material layer 220 on a substrate275. In the embodiment shown, the substrate 275 may be of conventionalheavy bond paper, cardboard, polymer or other suitable material tosupport handheld use of the ticket 100 as a scratch-off implement. Thatis, as indicated above, the loading material layer 101 is “scratch-off”in nature. Thus, in addition to incorporating a loading code 150 andmasking the underlying redeeming material layer 220 and redeeming codes250, 255, 257 (see FIG. 2A), it is also tailored with removability inmind.

Removability of the scratch-off loading material layer 101 involvesselecting a material and ensuring adhesion properties sufficient forremaining substantially in-tact during normal user handling andmanipulation in absence of scratch-off efforts while also furtheringscratching-off by the user when so desired. Available inks, the intendedvisual appearance of the loading code 150, material choices for theunderlying redeeming layer 220 or substrate 275, likely processingconditions and a host of other factors may play a role in the materialselected for the loading layer 101. Regardless, some tailoredcombination of conventional scratch-off inks and colored latex or otherpolymers may be utilized.

Continuing with reference to FIG. 2B, the redeeming material layer 220is shown as multi-layered with a transparent layer 260 over aninformation layer 230. In this embodiment, the transparent layer mayserve as a protective barrier to the physical scratch-off forces takenon by the ticket 100 during removal of the loading material layer 101(for example, by a coin as shown in FIG. 3A). In this way, the removalof the masking loading material 101 may take place without substantialdamage to redeeming code material 235. Given the see-through nature ofthe transparent layer 260, the redeeming codes 250, 255, 257, made up ofthe material 235, may thus be protected and also visibly revealed forsake of redemption as described above. Materials for the layers 260, 230of the redeeming code layer 220 may be selected based on these andprocessing conditions. For example, the transparent layer 260 may be asolid clear ink whereas the redeeming code material 235 may be of an inkprimarily tailored for permanency on the underlying substrate as opposedto being configured for scratching off.

The cross-section of FIG. 2B also reveals layers 280, 290 below thesubstrate 275. These may include a reactive layer 280 provided below thesubstrate 275 that is filled with microcapsules 285 of marking ink.Thus, similar to conventional carbonless papers, the microcapsules 285may be configured to burst upon exposure to stressors from the oppositeside of the substrate 275. Specifically, in this circumstance,scratch-off removal of the loading material layer 101 may translate intobursting of microcapsules within the reactive layer 280.

The reactive layer 280 may be sufficiently porous or of void space toallow for the visible presentation of the burst ink from themicrocapsules 285. At the same time, however, a partially clear, opaqueor transparent recording layer 290 below the reactive layer 290 may beprovided so as to prevent the used, scratched-off ticket 100 fromleaking ink onto the user or surrounding area while still being visibleto the ticket user. Thus, concern over mess, ink or other chemicalexposure to the user may be largely eliminated. In this regard, therecording layer 290 may also be absorbent to a degree that does notsubstantially impair the visibility of the noted marking of ascratched-off ticket 100. With brief added reference to FIG. 3B, uponscratch-off, marking 300 may be seen at the backside 325 of the ticket100.

Referring now to FIGS. 3A and 3B, front and back views of the ticket 100as might be seen during user “scratch-off” as described above are shown.Specifically, FIG. 3A is a front view of the ticket 100 of FIGS. 1 and2A revealing the underlying redeeming material layer's codes 250, 255,257 with partial scratch-off remains 101 left in the coded region 125.FIG. 3B, on the other hand, depicts a backside 325 of the ticket 100 ofFIG. 3A revealing indicator markings 300 corresponding to thescratching-off of the material 101 at the opposite side of the ticket100 as described above. The end result is that a ticket 100 that hasbeen scratched-off, and also most likely redeemed, will be highlightedwith visible markings on both sides thereof.

Whether the front side of the ticket 100 is visible to a user with onlyresidue 101 (FIG. 3A) or the backside 325 with markings 300 (FIG. 3B),the scratching-off will clearly be evidenced. In one embodiment, aparticularly distinct matching color choice, for example, a vibrant red,may be employed for both the redeeming code material 235 and the ink forthe markings 300 (see FIGS. 2B and 3B). Thus, from a user's perspective,the prominent display of what might be considered a “used” ticket 100would be readily apparent with visible exposed red codes 250, 255, 257at one side of the ticket 100 and red markings 300 at the other. In thissense, the ticket 100 provides an additional element ofuser-friendliness and an understanding aid to the user for what mightotherwise appear to be complex cryptocurrency management. Recallingthat, in circumstances where a retailer is responsible for loading theticket 100, the conventional purchasing user might only hold “unused”tickets 100 in loaded form. In these scenarios, the user would not onlyimmediately be able to decipher scratched-off used tickets 100 but alsobe aided in understanding that unmarked tickets 100 would most likely beloaded and unused. Of course, apart from just glancing at one side ofthe ticket 100 or the other, the user may take advantage of mobileapplication 401 to make such determinations certain (see FIG. 4).

Referring now to FIG. 4, an embodiment of a mobile device 400 is shownwith a user interface screen displaying an application 401 for use witha single-use cryptocurrency ticket 100 as described hereinabove. Thedevice 400 is equipped with a processor for functional use and interfacewith the ticket 100. For example, as alluded to above, with addedreference to FIGS. 1 and 2A, the user may check the loaded amount ofBitcoin via a scan of the loading 150 or redeeming 250 codes, dependingon which may be visible (see 430). Specifically, a particular amount ofBitcoin 450 and/or local currency 460 may be displayed at a real-timeconversion region 440.

With added reference to FIG. 1, apart from just running a preliminarycheck, the user may also redeem the ticket 100 by selecting the “redeem”category 415 of the application 401. With this category 415 selected andthe loading material layer 150 scratched off, the user may press thescan button for reading the visible redeeming code 250 from the ticket100 as shown in FIG. 5. Once read, the appropriate cryptocurrencyinformation may be displayed at the region 440 as noted above. Further,the user may select the redeem button 475 to complete the redemption. Infact, the application 401 may further serve as an electronic wallet forcontinued management of the redeemed cryptocurrency. Along these lines,note the wallet 425, address 480 and history 420 functions that may beincorporated into the application 401 to allow for ongoing management ofthe cryptocurrency long after the ticket 100 is used and discarded asbeing of no practical further value.

In one embodiment, the application 401 may also be used by a merchant,perhaps for loading of a ticket 100 as described above (see 410).Alternatively, merchants may be provided with a merchant specificapplication for this purpose, for example, with features to aid in thenear real-time acquisition and loading of Bitcoin so as to limitoverhead expenses. By the same token, in one embodiment, non-merchantusers may place orders for new tickets 100 that are un-loaded, similarto an order of blank bank checks. In this embodiment, the fullfunctionality of the application 401 may be utilized by the user forboth loading personally owned cryptocurrency as well as redeemingthrough the techniques discussed herein. Once more, whether for amerchant or self-loading user, the application 401 may be used to place“blank” unloaded ticket orders. Not only would this be safe in that thetickets 100 are unloaded during transit but it may also allow for thetickets 100 to be tracked as user specific, for example through theloading code 150, a serial number or other appropriate means if sodesired. In yet another embodiment, where users order their own “blank”tickets 100 as indicated, even the redeeming codes 250, 255, 257 may beuser-specific as an added security measure (e.g. to prevent redemptionby any other party). Ultimately, information in one of the codes 250,255, 257 (or 150) may be user-specific, merchant-specific or evenmonetary as indicated above for predetermining authorized users,merchants or even loading amounts.

Referring now to FIG. 5, a depiction of the page of the application 401of FIG. 4 for redeeming cryptocurrency via the redeeming code 250 isshown. As indicated above, the full functionality of the application 401with the ticket 100 may provide the user with a perspective similar tothat of using his or her hand 500 to load conventional paper currencyinto a conventional wallet. That is, while paper money may be acquiredand placed within a billfold, this is not an option in the world ofcryptocurrency. Yet, the ticket 100 may be acquired and figurativelyplaced within the device 400 wallet by merely scratching-off andredeeming. What is left behind is a scratched-off, marked up ticket 100on both sides that is no longer of any value. The user has placed themoney in the wallet regardless and in the process simultaneously clearlymarked the remnants as of no value (a used ticket 100). All that is leftis for the user to make proper, responsible disposal of the used ticket100. Please recycle.

Referring now to FIG. 6A, a schematic flow-chart summarizing anembodiment of assembling the ticket of FIG. 1 is shown. Specifically, asdescribed above, with a substrate available, a private redeeming codemay be printed on one side thereof as indicated at 610. A removable maskthat also serves as a one-time public loading code may then be adheredover the redeeming code as indicated at 620. Further, as noted at 630,at the other side of substrate, a reactive ink layer may be secured witha recording layer thereover. So, for example, scratch-off removing ofthe mask/loading code from the first side may be automatically marked atthe second opposite side of the single-use ticket which has now beenassembled (see 640).

Referring now to FIG. 6B, a flow-chart is now shown summarizing anembodiment of how to use the assembled ticket of FIG. 6A. Specifically,the masked private redeeming code may be activated as indicated at 660by loading of the noted loading code. Once this takes place, the loadingcode may be removed as indicated at 665. Thus, the underlying redeemingcode may be exposed so that the ticket may be utilized while at the sametime, further loading of the ticket via the loading code is disabled.Therefore, once redeemed as described below, there remains no practicalvalue to the ticket.

When the user is ready to redeem the value from the ticket via theredeeming code, he or she may do so directly or by sending the code toanother user at another location for redemption (see 670, 675). Auditoryand alphanumeric versions of the redeeming code may be particularlybeneficial for use when sending the code to a distant location forredemption. For example, a texted alphanumeric code may be readilyobtainable by a distant end user perhaps more so than a visual QR code.

Even though the value may be redeemed from the ticket, for example asrecorded at a ledger in the case of cryptocurrency, this redemptionvalue may continue to be managed even in absence of the ticket (see680). For example, a user may use a digital wallet application to managethe cryptocurrency going forward without continued use of the ticketwhich may now be discarded. Of course, as indicated at 685, rather thancontinuing to manage the cryptocurrency, it may be exchanged forpurchases or conversion to a local currency, the latter perhaps being alikely scenario where the redeeming code has been sent to a distantlocation for redemption.

Embodiments described hereinabove provide a manner of simplifying themanagement, use and understanding of cryptocurrency via a tangiblemedium. Specifically, a cryptocurrency user may be provided with a morefamiliar cash-like handheld instrument for cryptocurrency management.Once more, this is achieved in a manner that overcomes the potential foruser-confusion that may surround the fact that once the cryptocurrencyis spent, the corresponding tangible instrument or “ticket” does notautomatically depart from the user like conventional cash. Specifically,the spending of the cryptocurrency simultaneously physically convertsticket into a dramatically different instrument in appearance that mayno longer be used to manage cryptocurrency.

The preceding description has been presented with reference to presentlypreferred embodiments. Persons skilled in the art and technology towhich these embodiments pertain will appreciate that alterations andchanges in the described structures and methods of operation may bepracticed without meaningfully departing from the principle, and scopeof these embodiments. For example, while the focus of embodiments hereinsurround use of ticket embodiments for management of cryptocurrency,these tickets and applications may be applied to other forms ofinformation management. These may include titles, wills, or any numberof transfer, accounting processes for which a simplified single-use formof tangible instrument may serve as a beneficial managing tool foraiding user understanding, particularly where traditional handheldtickets/documents are being replaced by electronic versions thereof.Regardless, the foregoing description should not be read as pertainingonly to the precise structures described and shown in the accompanyingdrawings, but rather should be read as consistent with and as supportfor the following claims, which are to have their fullest and fairestscope.

1. A handheld single-use ticket for tangible management by a user, theticket comprising: a substrate; a redeeming material layer on thesubstrate; at least one redeeming code of the redeeming material layerfor accessing and using; a loading material layer masking over theredeeming code to prohibit the accessing, the loading material layer ofa removable material for enabling the accessing upon removing; and atleast one loading code of the loading material layer for loading theredeeming code for the using, the removing to prevent re-loading of theredeeming code via the loading code simultaneous with the enabling ofthe accessing.
 2. The handheld single-use ticket of claim 1 wherein theredeeming material layer comprises: an information layer comprisingmaterial for the at least one redeeming code; and a transparentprotective layer over the information layer for interfacing the loadingmaterial layer.
 3. The handheld single-use ticket of claim 1 wherein theredeeming material layer on the substrate is on a first surface of thesubstrate, the ticket further comprising: a reactive layer ofmicrocapsules on a second surface of the substrate opposite the firstsurface; marking ink of the microcapsules for releasing therefrom uponthe removing; and a recording layer on the reactive layer to protect theuser from exposure to the marking ink upon the releasing.
 4. Thehandheld single-use ticket of claim 1 wherein the loading material layerpresents the at least one loading code at a transparent filter of theloading material layer.
 5. The handheld single-use ticket of claim 4wherein the presented at least one loading code is supportably renderedby a code different from the at least one redeeming code, the differentcode at the redeeming material layer.
 6. The handheld single-use ticketof claim 4 wherein the transparent filter is a colored filter windowportion of the loading material layer.
 7. The handheld single-use ticketof claim 1 wherein the at least one redeeming code corresponds to acryptocurrency private key and the at least one loading code correspondsto a cryptocurrency public key.
 8. The handheld single-use ticket ofclaim 1 wherein the at least one redeeming code is selected from a groupconsisting of a visual code, an alphanumeric code and an auditory code.9. A system for single-use management of information by a user, thesystem comprising: a handheld ticket for tangible manipulation by theuser, the ticket having a redeeming code for accessing the informationand a loading code covering for associating the information with theredeeming code, access to the redeeming code prohibited by one of theloading code covering and another covering; an electronic device with aninterface screen to enable the user to access the information uponremoval of the one of the coverings; and a processor of the electronicdevice to store the information, the removal of the one of the coveringsto serve as an indicator to a user of the access to the information. 10.The system of claim 9 wherein the information is information relativeone of cryptocurrency rights, title rights, probate rights, asset rightsand access rights.
 11. A method of manufacturing a handheld single-useticket for tangible cryptocurrency management by a user, the methodcomprising: printing a private redeeming code on a given side of asubstrate for the cryptocurrency management; and adhering a publicloading code layer over the redeeming code to simultaneously enable theprivate redeeming code for the cryptocurrency management and prohibitaccess thereto.
 12. The method of claim 11 wherein the public loadingcode layer includes a window portion of a transparent filter forrendering a loading code from a code on the substrate and a maskingportion over the redeeming code.
 13. A method of managing cryptocurrencythrough a handheld single-use cryptocurrency ticket, the methodcomprising: activating a private redeeming code on the ticket byelectronic loading of a loading code layer on the ticket with a portionthereof that masks over the redeeming code; removing the loading codelayer to expose the redeeming code, the removing substantiallyprohibiting subsequent activating of the private redeeming code via theloading code; and redeeming the redeeming code for the managing of thecryptocurrency.
 14. The method of claim 13 further comprising sendingthe redeeming code to a user at a location distant from the ticket forthe redeeming thereof.
 15. The method of claim 14 wherein the redeemingcode is one of an alphanumeric code and an auditory code to support thedistant redeeming.
 16. The method of claim 13 further comprisingexchanging the cryptocurrency for one of a purchase and local currency.17. The method of claim 13 further comprising using an electronic walletapplication of a mobile device for the managing of the cryptocurrency inabsence of the ticket after the redeeming.
 18. The method of claim 13wherein the removing further comprises simultaneously and automaticallymarking a side of the ticket opposite the loading code with a markingink.
 19. The method of claim 13 further comprising encrypting one of apre-determined monetary information, user-specific information andmerchant-specific information into one of the loading code and theredeeming code in advance of the activating.
 20. The method of claim 13further comprising using an application of a mobile device to acquirecryptocurrency by a first party in a substantially simultaneous fashionwith the activating for a second party.